Bug fix making both focusers visible #1941
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Due to the underlying device name setting, the fact that FocusLynx has two independent drivers, its name setting does not work. With this fix the device names of the two focusers are fix to FocusLynx F1/F2.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to the underlying device name setting in combination with the fact that FocusLynx has two independent drivers, its name setting does not work. As a result, at least when FocusLynx is initialized through KStars locally, only the first focuser is visible. This could only be avoided if the INDI server is started manually.
With this fix the device names of the two focusers are fix to FocusLynx F1/F2, FocusLynx works with both focusers also in KStars local mode.